Method and system to automate payment for a commerce transaction

ABSTRACT

A method and system to automate payment for a network-based commerce transaction provide a buyer an option to enable an automatic payment service, wherein automatic payment service automatically provides payment to a seller upon a termination event of a network-based commerce transaction. Payment information of the buyer is provided to a network-based payment system upon the occurrence of the termination event.

CROSS-REFERENCE TO RELATED APPLICATION

This application is a divisional application of U.S. application Ser. No. 10/427,553 filed Apr. 30, 2003, which is incorporated in its entirety herein by reference.

FIELD OF THE INVENTION

The present invention relates generally to the field of network-based commerce and, more specifically, to a method and system to automate payment for a commerce transaction.

BACKGROUND OF THE INVENTION

With the wide spread acceptance of the Internet as an ubiquitous, interactive communication and interaction platform, on-line (or electronic) commerce conducted over the Internet has become commonplace in a variety of business environments. On-line commerce is traditionally categorized as business-to-business (B2B), business-to-consumer (B2C), consumer-to-consumer (C2C) and even business-to-employee (B2E) commerce. In the B2B environment, a number of online exchanges or marketplaces (e.g., vertical exchanges) have been established with a view to facilitating electronic commerce between parties, for example, within a vertical supply chain. Such B2B exchanges typically provide a number of tools for facilitating commerce, such as aggregated and near real-time inventory information, Requests for Quotation (RFQ) capabilities and auctions.

In the B2C and C2C environments, a number of marketplace exchanges and transaction facilities have proved popular. A leading electronic commerce system (or marketplace) is operated by eBay, Incorporated. Electronic marketplaces are also provided by Yahoo! Incorporated and Amazon.com. Further, a number of on-line services offer on-line classifieds, such as the Yahoo! Classifieds service offered by Yahoo! Incorporated.

A number of the on-line marketplaces are utilized by merchants as an important, if not a primary, distribution channel for products. Further, various retailers and merchants also utilize free, or low-cost, classified advertisement services offered on the Internet, such as Yahoo! Classifieds.

In order to complete the purchase of these products, buyers generally provide checkout information such as credit card numbers, checking account numbers and shipping addresses to the seller upon winning or completing the purchase. In the case of on-line auctions, sellers often wait days or weeks for the buyer's check out information, or never receive it at all and are forced to relist the item. Additionally, buyers forget to provide their checkout information.

SUMMARY OF THE INVENTION

A method and system to automate payment for a network-based commerce transaction have been disclosed. In one embodiment, a method comprises providing a buyer an option to enable auto-pay, wherein auto-pay automatically provides payment to a seller upon a termination event of a network-based commerce transaction. Payment information of the buyer is provided to a network-based payment system upon the occurrence of the termination event.

BRIEF DESCRIPTION OF THE DRAWINGS

The present invention is illustrated by way of example and not limitation in the figures of the accompanying drawings, in which like references indicate similar elements and in which:

FIG. 1 is a block diagram illustrating an exemplary network-based, according to one embodiment of the present invention.

FIG. 2 is a block diagram illustrating an exemplary network-based payment system environment, according to an exemplary embodiment of the present invention.

FIG. 3 is a database diagram illustrating an exemplary database maintained and accessed by a database engine server of the network-based commerce system.

FIG. 4 is a flow chart illustrating a method, according to an exemplary embodiment of the present invention, performed by the auto-pay module to complete a network-based commerce transaction.

FIG. 5 is a detailed flow chart illustrating a method, according to an exemplary embodiment of the present invention, performed by a commence system to accomplish a manual checkout.

FIG. 6 is a high-level flow chart illustrating a method, according to an exemplary embodiment of the present invention, performed by a commerce system to checkout using auto-pay.

FIG. 7 illustrates a graphical user interface that is presented to a buyer to facilitate entry of electronic payment information.

FIG. 8 illustrates a graphical user interface that is presented to a seller as confirmation of the end of an auction implementing auto-pay.

FIG. 9 illustrates a graphical user interface that is presented to a buyer when the buyer wins an auction implementing auto-pay.

FIG. 10 is a high-level flow chart illustrating a method, according to an exemplary embodiment of the present invention, performed by an auto-pay module to determine if auto-pay is available.

FIG. 11 illustrates a graphical user interface presented to a buyer that is an auto-pay panel that lists multiple items the buyer is bidding on.

FIG. 12 illustrates a display showing confirmation that auto-pay is enabled by a buyer for a particular listing.

FIG. 13A illustrates an exemplary graphical user interface of a listing having auto-pay available to the buyer.

FIG. 13B illustrates an exemplary graphical user interface of a bid confirmation page.

FIG. 13C illustrates an exemplary graphical user interface to review a buyer's auto-pay shipping and payment information.

FIG. 13D illustrates an exemplary graphical user interface that allows a buyer to view his/her auto-pay setting.

FIG. 14 illustrates an exemplary graphical user interface for a seller enabling auto-pay

FIG. 15 illustrates a high-level flow chart illustrating a method according to an exemplary embodiment of the present invention, performed for seller-driven auto-pay.

FIG. 16 shows a diagrammatic representation of a machine in the exemplary form of a computer system within which a set of instructions, for causing the machine to perform any one of the methodologies discussed above, may be executed.

DETAILED DESCRIPTION

A method and system to automate payment for commerce transactions are described. In the following description, for purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of the present invention. It will be evident, however, to one skilled in the art that the present invention may be practiced without these specific details.

Terminology

The term “user” shall be taken to refer to any entity, human or automated, that contributes to, or participates in, a transaction, communication or process.

The term “transaction” shall be taken to include any communication or exchange between two or more parties with a view to establishing a business agreement, exchange of value or a commercial relationship. Accordingly, the word “transaction” shall be deemed to cover, but not be limited to, a purchase-and-sale transaction established as a result, for example, of the placement of an advertisement or as a result of the conclusion of an auction process, the auction process being conducted on-line or otherwise.

While an exemplary embodiment of the present invention is discussed below with reference to “items”, it will be appreciated that the present invention is not so limited. Accordingly, the word “item” shall be deemed to cover, but not be limited to, a transaction listing, in which both items and services may be included.

Commerce System

FIG. 1 is a block diagram illustrating a commerce system 100, and the software and hardware components of a network-based marketplace machine 10, a client machine 38, and a partner machine 8, according to an exemplary embodiment of the present invention. The system 100 includes the client machine 12, and the network-based marketplace machine 10, that communicate via a network 22. The network 34 may be embodied as Internet, a LAN, a WAN, PSTN, Frame Relay, ATM, satellite communications, wireless communications, combinations thereof, or any other network equipment or protocol that enables electronic communication between the above described network entities.

The client machine 38 enables the client to access services that are provided by the network-based marketplace machine 10 and, a payment machine 8, illustrated more fully in FIG. 2.

The network-based marketplace machine 10 provides online marketplace services that enable sellers and buyers to transact items and services. A buyer that submits a winning bid in an auction or executes a purchase to complete a sale may acquire goods and/or services from the seller.

In one embodiment the network-based marketplace machine 10 may be embodied as “eBay The World's Online Marketplace”™ created by eBay of San Jose, Calif.

The payment machine 8 provides payment services that enable a user to electronically send and receive payments over the network 34. For example, the payment machine 16 may be embodied as the PayPal™ Payment Service operated by PayPal of San Jose, Calif. Additional embodiments of payment machine 16 may be Western Union® BidPay™ Payment Service operated by BidPay.com, Inc. of Bridgeton, Mo.; Bill Me Later® operated by I⁴ Commerce™ of Timonium, Md.; or other similar electronic payment systems. In alternate embodiments, payment machine 8 is integrated with network-based marketplace machine 10.

In addition to other software components that are not illustrated, the client machine 38 includes a client communication program 36. The client communication program 36 enables a user to display web pages or e-mail messages that are loaded from server computers. The client communication program 36 may be embodied as a browser (e.g., the Microsoft Internet Explorer browser developed by Microsoft™ Corporation of Richmond, Wash. or Navigator™ browser developed by Netscape of Mountain View, Calif.). The client communication program 36 executes under an operating system (e.g., Microsoft™ Windows developed by Microsoft™ Corporation or Mac OS X developed by Apple Computer of Cupertino, Calif.) The client communication program 36 may also be embodied as a mail client (e.g., the Microsoft Outlook personal information manager developed, by Microsoft™ Corporation of Richmond, Wash. or Lotus Notes™ developed by the Lotus Notes Development Corporation.

The network-based marketplace machine 10 includes one or more of a number of types of front-end servers, namely communications servers in the exemplary form of an application program interface (API) servers 13, page servers 12 that deliver web pages (e.g., markup language documents), picture servers 14 that dynamically deliver images to be displayed within Web pages, listing servers 16, processing servers in the exemplary form of CGI (or ISAPI) servers 18 that provide an intelligent interface to back-end servers, and search servers 20 that handle search requests to the network-based marketplace machine 10. The e-mail servers 22 provide, inter alia, automated e-mail communications to users of the network-based marketplace machine 10. The ISAPI servers 18 host an auto-pay module 44. Although illustrated as part of ISAPI servers 18, auto-pay module 44 can be distributed throughout the servers of the network based market machine 10, as well as embodied as an independent server. Auto-pay module 44 allows for the use of auto-pay. When auto-pay is used, a network-based commerce transaction is automatically completed. In other words, money is automatically transferred from a purchaser's financial account to the seller's financial account because the purchaser and seller have both provided their respective information, prior to the close of the transaction.

The back-end servers include a database engine server 26, a search index server 24 and a credit card database server 28, each of which maintains and facilitates access to a respective database.

FIG. 2 is a block diagram illustrating hardware components of the payment machine 8 utilized by the system 100, according to an exemplary embodiment of the present invention. The payment machine 8 includes one or more of a number of types of front-end servers, namely communications servers in the exemplary form of an application program interface (API) servers 80, page servers 82 that deliver web pages (e.g., markup language documents), processing servers in the exemplary form of CGI (or ISAPI) servers 84 that provide an intelligent interface to back-end servers. The e-mail servers 66 provide, inter alia, automated e-mail communications to users of the payment machine 168. The back-end servers include database engine servers 68 that maintains and facilitates access to a database 70.

Database Structure

FIG. 3 is a database diagram illustrating an exemplary database 30 maintained and accessed via a database engine server 26 that supports the network-based marketplace machine 10. The database 30 may, in one embodiment, be implemented as a relational database, and includes a number of tables having entries, or records, that are linked by indices and keys. In an alternative embodiment, the database 30 may be implemented as a collection of objects in an object oriented database.

The database 30 includes a user table 54 that contains a record for each user of the network-based marketplace machine 10. The user may operate as a seller, buyer, or both, with respect to the network-based marketplace machine 10. The database 30 also includes listings table 60 that may be linked to the user table 54 and a listing association table 52. A user record in the user table 54 may be linked to multiple items that are being, or have been, transacted via the network-based marketplace machine 10.

The number of other tables are also shown to be linked to the user table 54, namely a user past aliases table 48, a feedback table 50, a bids table 55, an account table 64, an account balances table 62 and a purchase history table 58. The masters categories table 67 stores records for listing categories presented across multiple views (or presentations) of list categories via regional or community sites presented by the network-based marketplace machine 10. A site categories table 42 stores records indicating which item categories are to be presented for respective regional or community sites (e.g., a country, region or city specific site) presented by the network-based marketplace machine 10.

FIG. 4 is a flow chart illustrating a method 400, according to an exemplary embodiment of the present invention, performed by the marketplace machine 10 to establish a network-based commerce transaction. The method 400 commences at block 401. At block 410, a user requests that a network-based commerce transaction be established. The request can be any of a multitude of user-initiated or system-initiated events. For example, the user can be a winning bidder, and the network-based commerce transaction can be an on-line auction. The user's request is automatically generated by marketplace machine 10, once the on-line auction closes and the user is identified as the highest bidder. During the pendancy of the on-line auction, database engine server 26 maintains listings table 60 including all the tables that support the listings, such maintenance including updating bids stored in bids table 55 from various bidders. Additionally, database engine server 26 maintains an auto-pay settings table 71 for each record in the listings table 60. Auto-pay settings table 71 indicates whether the transaction is to be completed using auto-pay.

Thus, when a request to complete a network-based commerce transaction is generated, at block 410, the auto-pay module 44 determines if auto-pay should be used at decision block 420, by examining auto-pay settings table 71. If the auto-pay table 71 indicates that auto-pay should not be used, then a manual checkout process is used to complete the network-based commerce transaction at block 430. If the auto-pay table 71 indicates that auto-pay should be used, then auto-pay module 44 is used to complete the network-based commerce transaction at block 440. The process ends at block 499.

FIG. 5 is a detailed flow chart illustrating a method 500, according to an exemplary embodiment of the present invention, performed by marketplace machine 10, to accomplish a manual checkout. FIG. 5 uses as an example the checkout process upon winning an on-line auction. The method 500 commences at block 501 where a user, having received notification that the transaction obligations have been established, views the listing 70 via browser application 36. At block 502, the user logs-in and communicator module 75 verifies the user's identity. Marketplace machine 10 provides the user with a bid confirmation upon successful login at step 503.

At decision block 504, the marketplace machine 10 prompts the user 10 to respond whether his/her shipping address is within the United States. If the address is not within the United States, the user enters a shipping address in the United States at block 505. Upon entry of a United States address or if the address was a valid United States address, the marketplace machine 10 determines at block 506 if the buyer (user) is registered with an electronic payments system such as payment machine 8. If the user is not registered, the user is prompted to provide credit card information at block 507. At decision Hock 508, the marketplace machine 10 determines if the information provided by the user passes a standard credit card authorization process. If the authorization is not provided, a credit card page indicating the authorization error is provided to the user and the user is provided another opportunity to provide credit card information at block 507.

If credit card authorization is provided at decision block 508, then a reviewer page 72 is generated at block 512. At decision block 520, the marketplace machine 10 determines if the buyer is registered with an Electronic Payments (EP) System such as payment machine 8. If the buyer is registered, then an auto-pay confirmation is provided to the buyer at block 521. The buyer's financial account is debited and the seller's account is credited at block 523. If the buyer was not registered with an electronic payment system at decision block 520, then the buyer is still provided an auto-pay confirmation at block 522. Additionally, the buyer provided with the option to register with an electronic payment system. The registration process is completed at block 524 according to steps required by the specific EP system used and funds are transferred at block 523. Interactions with payment machine 8 may be necessary with blocks 520-524.

Returning to decision block 506, if the buyer is registered with an electronic payment system, a review page is provided to the buyer at block 511. After confirmation of the transaction, funds flare transferred from the buyer to the seller at block 523. The process ends at block 599.

FIG. 6 is a high-level flow chart illustrating a method 600, according to an exemplary embodiment of the present invention, performed by marketplace machine 10, to checkout using auto-pay. The method 600 commences at block 601 and can be implemented within block 440 of FIG. 4. Prior to executing method 600, a seller has established an electronic payment account to which payment will be received. For example, the seller established an account with payment machine 8. The buyer's shipping address can be stored in account table 64 through the processing flow of processing block 505 of FIG. 5. The form of electronic payment can be stored in auto-pay settings table 71 through the processing flow of processing block 524 of FIG. 5. Additionally, the buyer has already configured his auto-pay account with a shipping address and a form of electronic payment.

Thus, at block 610, once a buyer has won an auction (or otherwise incurred a payment obligation), the marketplace machine 10 automatically provides the seller with the buyer's shipping address as the buyer provided above. The seller receives the buyer's payment information automatically at block 620. Prior to this transmission of payment information, the buyer provided his or her credit card information, and registered with payment machine 8. FIG. 7 illustrates a graphical user interface 7000 that can be presented to a buyer to facilitate entry of electronic payment information. Although credit card information is requested, other electronic payments are contemplated, including payments via electronic mail, tend electronic checks. Thus, the seller can receive the buyer's credit card information, or information regarding any other form of electronic payment. For example, the buyer's information can be provided directly to PayPal or a similar banking institution.

Returning to FIG. 6, at block 630, confirmations are provided to the buyer and seller for the purchase. FIG. 8 illustrates an exemplary, graphical user interface 8000 that can be presented to a seller as confirmation of the end of an auction implementing auto-pay. Interface 8000 states to the seller that the buyer has selected to use auto-pay. FIG. 9 illustrates an exemplary graphical user interface 9000 that can be presented to a buyer of the winning of an auction implementing auto-pay. Interface 9000 states to the buyer a reminder that the transaction will be completed using auto-pay. Both interface 8000 and 9000 can be e-mails to the seller and buyer respectively. Additionally, both interfaces of FIGS. 8 and 9 are generated via auto-pay module 44. The method ends at block 699.

Once an auction closes, the marketplace machine 10 determines if auto-pay is on and can be used for checkout. FIG. 10 is a high-level flow chart illustrating a method 700, according to an exemplary embodiment of the present invention, performed by auto-pay module 44, to determine if auto-pay should be used and if auto-pay is available for checkout purposes. The method 700 commences at block 701. Method 700 can be used to implement decision block 420 of FIG. 4.

At block 710, auto-pay module 44 checks if the seller globally disabled the auto-pay feature within his or her user profile by checking a global disable auto-pay field in auto-pay settings table 71. If auto-pay is globally disabled, it is determined that auto-pay is off at block 740 and the process ends at block 799. If auto-pay is off a manual checkout is performed according to block 430 of FIG. 4.

If auto-pay is not globally disabled, auto-pay module 44 determines if the seller enabled auto-pay for the particular listing at decision block 720. Auto-pay module 44 checks an auto-pay enabled field in listings table 60. If the seller did not enable auto-pay for the particular listing, then the process continues to block 740, as described above. At decision block 720, additional conditions can be imposed upon the seller. For example in order to enable auto-pay, shipping costs can be required to be provided, as well as tax and insurance costs.

If the seller enabled auto-pay for the particular listing and provided any required costs, then at decision block 730, auto-pay module 44 determines if the buyer enabled his payment via auto-pay for the specific listing. Auto-pay settings table 71 stores information regarding whether the buyer enabled auto-pay. If the buyer did not enable auto-pay then the process continues to block 740 as discussed above. If the buyer did enable auto-pay, then module 44 determines that auto-pay is on at block 750 and method 600 is completed. Also at block 750, upon determining that auto-pay is on, the auto-pay settings table 71 can be updated to reflect that auto-pay is or is not on and the payment flow of FIG. 6 is used. The process completes at block 799.

In an alternate embodiment, the seller can be left completely unaware of the fact that the buyer used auto-pay. In this embodiment, the seller has specified that he accepts credit card payments (or any similar type of instant funds transfer), and has specified the total cost of the item (including shipping costs, either fixed or actual). The buyer uses auto-pay to complete the transaction and the seller receives payment immediately once the listing ends. Furthermore, default settings can be established to allow auto-pay automatically.

FIG. 11 illustrates an exemplary graphical user interface (GUI) 1100 presented to a buyer that lists multiple items that he or she is bidding on. Interface 1100 displays whether auto-pay is on or off for each item listed. By manipulating GUI 1100 the buyer enables (or disables) auto-pay for a particular listing. The buyer's decision is queried at decision block 730 a discussed above in connection with FIG. 10.

Item 2108691703 is listed in FIG. 11. The auto-pay status column indicates that auto-pay is on for the listing and can be turned off by the user. Shipping and payment information can be updated for item 2108691703 as illustrated in GUI 1100.

Item 1122334455 is also listed in FIG. 11. The auto-pay status column indicates that auto-pay is off. The buyer is losing the auction and can bid again, and offer a higher price than the current price. If the buyer re-submits a bid auto-pay can be turned on and a confirmation page can be displayed as shown in FIG. 12.

The listing for item 2107951143, indicates that the buyer has not enabled auto-pay. However, since the buyer is winning the auction, he/she can turn on auto-pay. By turning on auto-pay settings table 71 will be updated. Additionally, the buyer will be prompted to enter his/her shipping address and electronic payment service information.

The listing for item 2111518219 indicates that auto-pay is not available to the buyer. Auto-pay may be unavailable because the seller globally disabled auto-pay as discussed above in reference to decision block 710 of FIG. 10. Additionally, auto-pay may be unavailable because the seller disabled auto-pay for the specific listing.

Additionally, auto-pay can be used whenever the on-line auction closes, even when items are bought for a fixed price, through a buyout mechanism, such as “Buy it Now” used by eBay Inc. within the marketplace it operates. In this scenario a buyer can provide all his or her checkout information and then later decide to end the auction and purchase the item for a fixed-price. “Buy it Now” is also available as part of a fixed-price listing, where there is no auction element at all. The auto-pay module 44, completes the transaction using the previously entered checkout information.

FIGS. 13A-13D illustrate exemplary graphical user interfaces for initializing and using auto-pay. FIG. 13A illustrates an exemplary graphical user interface 1301 of a listing having auto-pay available to the buyer. GUI 1301 includes an auto-pay link 1302 which the buyer can click-on. By following auto-pay link 1302, the buyer can provide electronic payment system and shipping information needed to complete the marketplace transaction using auto-pay.

FIG. 13B illustrates an exemplary graphical user interface 1320 of a bid confirmation page. GUI 1320 is presented to a buyer when auto-pay is available for a listing, but has not yet been turned on by the buyer. GUI 1321 includes an auto-pay link 1321 which the buyer can click on to enable auto-pay. By following link 1321, the buyer can provide electronic payment system information and shipping information needed to complete the marketplace transaction using auto-pay.

FIG. 13C illustrates an exemplary graphical user interface 1350 to review a buyer's auto-pay shipping and payment information. GUI 1350 includes a submit button 1351, which when clicked enables auto-pay by the buyer for the particular listing. Payment block 1352 indicates the use of a credit card payment, however various embodiments are contemplated that utilize payment systems such as payment machine 8.

FIG. 13D illustrates an exemplary graphical user interface 13 that allow a buyer to view his/her auto-pay setting. GUI 1380 shows a buyer all listing that he/she is currently bidding on. Auto-pay setting link 1380, when selected by the buyer allows him/her to edit his/her auto-pay settings as stored in auto-pay settings table 71. The auto-pay settings may be edited on a GUI, such as GUI 1100 of FIG. 11.

FIG. 14 illustrates an exemplary graphical user interface 1400 for a seller enabling auto-pay. GUI 1400 includes for a payment address and additional information required to generate a listing on marketplace machine 10. Additionally, GUI 1401 includes an allowed auto-pay check box 1401 which the seller selects to allow buyers to complete transactions using auto-pay. If check box 1401 is not selected, decision block 720 of FIG. 10 results in the negative. Thus, various GUIs shown in FIGS. 13A-13D and FIG. 14 have been presented as one embodiment of initiating auto-pay.

In an additional embodiment, commerce system 100 can be used to enforce a seller driven auto-pay network-based transaction process. With seller driven auto-pay, the seller requires payment before the transaction can end successfully or after an item has been claimed. For example, before a listing for an auction item closes, payment is provided to the seller.

A GUI similar to GUI 1100 can be presented to the seller for each listing he/she has. Such a GUI would also include an auto-pay status column that allows the seller to turn of auto-pay for each listing. For each listing, the seller can chose to require that the buyer pay in real time or have a stored payment profile (including credit cards) in order to successfully purchase or bid on a listing. FIG. 15 illustrates a high-level flow chart illustrating a method 1500, according to an exemplary embodiment of the present invention, performed for seller-driven auto-pay. The method 1500 commences at block 1501. At processing block 1510 a request from the buyer to initiate a purchase or bid associated with a network-based commerce transaction is received by auto-pay module 44. The network-based commerce transaction can be an auction having an immediate purchase item, a fixed price listing allowing immediate purchase by a private seller, or a fixed price listing allowing immediate purchase from an on-line retailer.

At decision block 1520, auto-pay module determines if the seller required the buyer use auto-pay for the particular listing. If auto-pay is not required, the buyer is prompted to complete the purchase, or enter a bid without invoking auto-pay at processing block 1530. The process would end at block 1599.

If the seller does require the buyer to use auto pay, auto-pay module 44 determines if the seller requires immediate manual payment or payment via information stored in the buyer's profile? If immediate manual payment processing is required, then at processing block 1550 the buyer is stepped through the process of paying with immediately available funds (e.g., account balance, instant funds transfer guaranteed by payment system, or credit card). The transaction is closed at processing block 1570 and the process terminates at block 1599.

If information stored in the buyer's profile is required for payment, such information is retrieved at processing block 1560. The information is used to process the payment (using payment system 8 if necessary). The transaction is closed at processing block 1570 and the process terminates at block 1599.

It is important to note that in this embodiment payment from the buyer to seller occurs before the auction closes. If a buyer can not make payment, then the auction remains open. In one embodiment of the payment processing flow of blocks 1550 and 1560, the item is not placed on hold, so it remains available to other prospective buyers. This allows for a “race” condition between two or more buyers. In an alternate embodiment, the listing is put on hold.

Payment processing flow of block 1550 and 1560 can involve numerous actions. For example, a bidder can be directed to payment system 8 to complete the transaction. Once payment system 8 collects and applies the buyer's payment information, confirms that the item is still available, it processes the payment and closes the listing. If multiple items are available, the quality available is decremented. Additionally, if the buyer is not previously registered with payment system 8, the buyer goes through the registration flow unique to payment system 8. It is important to note that payment processing information can be stored on marketplace machine 10 and provided to payment system 8, just prior to the conclusion of the transaction to streamline line the payment process. This can be achieved by querying the buyer to use his/her stored payment processing profile. Information in the profile can be stored in user table 54 and tables of database 30.

Marketplace machine 10 in conjunction with payment machine 8 cart have additional functionalities. These functionalities, as will be described in greater detail below include the use of confirmed shipping addresses, specific currency requirements, flexible payment timing, unpredictable final price payments, quick cash pricing options, and non-cash payment facilitation.

A confirmed shipping address can be an address that matches an address stored on file or verified with payment system 8. Additionally, an address can be confirmed based on a minimum buyer feedback/reputation score, a price range, or a seller chosen pre-approved buyer list.

The flexible timing functionality allows that at the seller's discretion, or based on the format, payment can occur after the close of item. For example, the seller can require that payment be made within 48 hours of the end of an item. This can happen in realtime, where the buyer enters payment information as described above. Alternatively, the seller can require that the buyer have a stored payment profile and an attempt to automatically process a payment can be made immediately, again in 24 hours in the event of a failure, and perhaps one last time 24 hours after that if a failure condition persists.

The unpredictable final price functionalities allows for cases where the final price cannot be known until the end of the listing (e.g., in an auction format, or a volume-discount multi-item purchase), the seller can apply different auto-pay rules. For example, if the final price exceeds $100, he or she can require immediate payment, but allow for a within-48-hours automatic payment if the price is less than $100.

The quick cash pricing option allows a seller to specify a start price (i.e., opening bid), an immediate purchase price (i.e., price at which the buyer can immediately purchase, resulting in the closing of the item), and a reserve price (i.e., price the buyer must meet or exceed before he or she can claim the item). Another pricing option is the Quick Cash price.

For example, the seller may list a PSA 10 Jason Giambi Alaska League rookie card with the following pricing options:

start price: $9.99

quick cash price: $200

reserve price (non-quick-cash): $$300

immediate purchase price: $500

The card can be sold in a variety of ways, including these two examples:

-   -   Buyer 1: Wins via auction, with a winning bid of $400. The item         closes and the buyer intends to pay with a cashier's check, to         be sent to the seller in a few days. The buyer changes his mind         the next day, though, leaving the seller with a non-paying         bidder. Alternatively, the seller sends a second-chance offer to         the net highest bidder, who sends him a cashier's check the next         day for $390.     -   Buyer 2: Agrees to a Quick Cash purchase, meaning that an         auto-pay payment is made and the listing is ended when the         buyer's payment of $200 is successfully processed.

Finally, system 100 allows for the processing of a non-cash payment (e.g., a trade). For example, just as payment system 8 maintains a payment profile for its customers, a baseball card storage facility maintains a portfolio of baseball cards for its customers (stored in a temperature-controlled vault, the ownership of these cards can be transferred without the cards ever leaving the vault). A seller can list an item “for sale for $3,000 immediate cash payment, or trade for ownership transfer of PSA 9 Mickey Mantle rookie card.” Upon receiving notification that either $3,000 or the Mantle card had been deposited in his or her account, the seller would send the item to the buyer.

FIG. 16 shows a diagrammatic representation of machine in the exemplary form of a computer system 800 within which a set of instructions, for causing the machine to perform any one of the methodologies discussed above, may be executed. In alternative embodiments, the machine may comprise a network router, a network switch, a network bridge, Personal Digital Assistant (PDA), a cellular telephone, a web appliance, set-top box (STB) or any machine capable of executing a sequence of instructions that specify actions to be taken by that machine.

The computer system 800 includes a processor 802, a main memory 806 and a static memory 808, which communicate with each other via a bus 824. The computer system 800 may further include a video display unit 812 (e.g., a liquid crystal display (LCD) or a cathode ray tube (CRT)). The computer system 800 also includes an alphanumeric input device 814 (e.g., a keyboard), a cursor control device 816 (e.g., a mouse), a disk drive unit 818, a signal generation device 822 (e.g., a speaker) and a network interface device 810.

The disk drive unit 818 includes a machine-readable medium 820 on which is stored a set of instructions (i.e., software) 804 embodying any one, or all, of the methodologies described above. The software 804 is also shown to reside, completely or at least partially, within the main memory 806 and/or within the processor 802. The software 804 may further be transmitted or received via the network interface device 810. For the purposes of this specification, the term “machine-readable medium” shall be taken to include any medium which is capable of storing or encoding a sequence of instructions for execution by the machine and that cause the machine to perform any one of the methodologies of the present invention. The term “machine-readable medium” shall accordingly be taken to included, but not be limited to, solid-state memories, optical and magnetic disks, and carrier wave signals. Further, while the software is shown in FIG. 16 to reside within a single device, it will be appreciated that the software 804 could be distributed across multiple machines or storage media, which may include the machine-readable medium.

Thus, a method and system automate payment for a commerce transaction has been described. Although the present invention has been described with reference to specific exemplary embodiments, it will be evident that various modifications and changes may be made to these embodiments without departing from the broader spirit and scope of the invention. Accordingly, the specification and drawings are to be regarded an illustrative rather than a restrictive sense.

In the foregoing detailed description, the method and system of the present invention has been described with reference to specific exempla embodiments thereof. It will, however, be evident that various modifications and changes may be made thereto without departing from the broad spirit and scope of the present invention. In particular, the separate blocks of the various block diagrams represent functional blocks of methods or apparatuses and are not necessarily indicative of physical or logical separations or of an order of operation inherent in the spirit and scope of the present invention. The present specification and figures are accordingly to be regarded as illustrative rather than restrictive. 

1. A method comprising: interfacing with a network-based commerce system configured to interact with a network-based payment system via a data network; receiving, at the network-based commerce system by use of a data processor, payment information related in part to a first electronic payment account associated with a first party, the first electronic payment account having been previously established at the network-based payment system, the payment information including information related to a second electronic payment account associated with a second party, the second electronic payment account having been previously established at the network-based payment system; receiving, at the network-based commerce system by use of the data processor, a request to complete a network-based commerce transaction upon occurrence of a termination event at the network-based commerce system, the termination event and a particular listing corresponding to the network-based commerce transaction; determining if the first party is registered with the network-based payment system; determining if the second party has disabled automatic payment for transactions corresponding to the particular listing while enabling automatic payment for transactions corresponding to different listings; determining if information provided by the first party can be confirmed based on a provided address; and automatically sending, by use of the data processor, the payment information to the network-based payment system in a data network communication upon the occurrence of the termination event, if the first party is registered with the network-based payment system, if the second party has enabled automatic payment for transactions corresponding to the particular listing, and if information provided by the first party can be confirmed based on a provided address, the sending of the payment information causing a transfer of funds at the network-based payment system from the first electronic payment account to the second electronic payment account.
 2. The method of claim 1, further including enabling the first party to disable the automatic sending of the payment information, edit the payment information, and edit a shipping address.
 3. The method of claim 1, wherein the network-based commerce transaction is one or more of a network-based auction, a fixed-price sale of an item from a private individual a fixed-price sale of an item from an network-based store, and an on-line barter transaction.
 4. The method of claim 1, wherein the payment information is selected from a group including a credit card number, a checking account number, a shipping address and an e-mail address.
 5. The method of claim 1, further comprising enabling the second party to disable the automatic sending of the payment information.
 6. The method of claim 1, further comprising receiving the payment information prior to the termination event.
 7. The method of claim 1, further comprising storing the payment information for future network-based commerce transactions.
 8. The method of claim 1, further comprising providing the first party an option to always use the payment information for future network-based commerce transactions.
 9. A system comprising: means for interfacing with network-based commerce system configured to interact with a network-based payment system via a data network; means for receiving, at the network-based commerce system by use of a data processor, payment information related in part to a first electronic payment account associated with a first party, the first electronic payment account having been previously established at the network-based payment system, the payment information including information related to a second electronic payment account associated with a second party, the second electronic payment account having been previously established at the network-based payment system; means for receiving, at the network-based commerce system by use of the data processor, a request to complete a network-based commerce transaction upon occurence of a termination event at the network-based commerce system, the termination event and a particular listing corresponding to the network-based commerce transaction; means for determining if the first party is registered with the network-based payment system; means for determining if the second party has disabled automatic payment for transactions corresponding to the particular listing while enabling automatic payment for transactions corresponding to different listings; means for determining if information provided by the first party can be confirmed based on a provided address; and means for automatically sending, by use of the data processor, the payment information to the network-based payment system in a data network communication upon the occurrence of the termination event, if the first party is registered with the network-based payment system, if the second party has enabled automatic payment for transactions corresponding to the particular listing, and if information provided by the first party can be confirmed based on a provided address, the sending of the payment information causing a transfer of funds at the network-based payment system from the first electronic payment account to the second electronic payment account.
 10. The system of claim 9, being further configured to enable the first party to disable the automatic sending of the payment information, edit the payment information, and edit a shipping address.
 11. The system of claim 9, wherein the network-based commerce transaction is one or more of a network-based auction, a fixed-price sale of an item from a private individual, a fixed-price sale of an item from an network-based store, and an on-line barter transaction.
 12. The system of claim 9, wherein the payment information is selected from a group including a credit card number, a checking account number, a shipping address and an e-mail address.
 13. The system of claim 9, further comprising means for enabling the second party to disable the automatic sending of the payment information.
 14. The system of claim 9, further comprising means for receiving the payment information prior to the termination event.
 15. The system of claim 9, further comprising means for saving the payment information for future network-based commerce transactions.
 16. The system of claim 9, further comprising means for providing the first party an option to always use the payment information for future network-based commerce transactions.
 17. A network-based system comprising: a marketplace machine configured to receive data from a data network and to send data to the data network, the marketplace machine including: a data processor having access to the data network, a database engine server, and an automatic payment service module; wherein the marketplace machine interfaces with a network-based commerce system configured to interact with a network-based payment system via the data network, the marketplace machine further to receive payment information related in part to a first electronic payment account associated with a first party, the first electronic payment account having been previously established at the network-based payment system, the payment information including information related to a second electronic payment account associated with a second party, the second electronic payment account having been previously established at the network-based payment system, the marketplace machine further to receive a request to complete a network-based commerce transaction upon occurrence of a termination event at the network-based commerce system, the termination event and a particular listing corresponding to the network-based commerce transaction, the marketplace machine further to determine if the first party is registered with the network-based payment system, determine if the second party has disabled automatic payment for transactions corresponding to the particular listing while enabling automatic payment for transactions corresponding to different listings, and determine if information provided by the first party can be confirmed based on a provided address, and the marketplace machine further to automatically send the payment information to the network-based payment system in a data network communication upon the occurrence of the termination event, if the first party is registered with the network-based payment system, if the second party has enabled automatic payment for transactions corresponding to the particular listing, and if information provided by the first party can be confirmed based on a provided address, the sending of the payment information causing a transfer of funds at the network-based payment system from the first electronic payment account to the second electronic payment account.
 18. The network-based system of claim 17, being further configured to enable the first party to disable the automatic sending of the payment information, edit the payment information, and edit a shipping address.
 19. The network-based system of claim 17, wherein the network-based commerce transaction is one or more of a network-based auction, a fixed-price sale of an item from a private individual, a fixed-price sale of an item from an network-based store, and an on-time barter transaction.
 20. The network-based system of claim 17, wherein the payment information is selected from a group including a credit card number, a checking account number, a shipping address and an e-mail address.
 21. The network-based system of claim 17, wherein the marketplace machine is configured to enable the second party to disable the automatic sending of the payment information.
 22. The network-based system of claim 17, wherein the marketplace machine is configured to receive the payment information prior to the termination event.
 23. The network-based system of claim 17, wherein the database engine server saves payment information for future network-based commerce transactions.
 24. The network-based system of claim 17, wherein the marketplace machine provides the first party an option to always use the payment information for future network-based commerce transactions.
 25. A non-transitory computer-readable storage medium for storing a sequence of instructions that, when executed by a machine, cause the machine to: interface with a network-based commerce system configured to interact with a network-based payment system via a data network; receive, at the network-based commerce system, payment information related in part to a first electronic payment account associated with a first party, the first electronic payment account having been previously established at the network-based payment system, the payment information including information related to a second electronic payment account associated with a second party, the second electronic payment account having been previously established at the network-based payment system; receive, at the network-based commerce system, a request to complete a network-based commerce transaction upon occurrence of a termination event at the network-based commerce system, the termination event and a particular listing corresponding to the network-based commerce transaction; determine if the first party is registered with the network-based payment system; determine if the second party has disabled automatic payment for transactions corresponding to the particular listing while enabling automatic payment for transactions corresponding to different listings; determine if information provided by the first party can be confirmed based on a provided address; and automatically send the payment information to the network-based payment system in a data network communication upon the occurrence of the termination event, if the first party is registered with the network-based payment system, if the second party has enabled automatic payment for transactions corresponding to the particular listing, and if information provided by the first party can be confirmed based on a provided address, the sending of the payment information causing a transfer of funds at the network-based payment system from the first electronic payment account to the second electronic payment account.
 26. The computer-readable storage medium of claim 25, wherein the sequence of instructions being further configured to cause the machine to enable the first party to disable the automatic sending of the payment information, edit the payment information, and edit a shipping address.
 27. The computer-readable storage medium of claim 25, wherein the network-based commerce transaction is one or more of a network-based auction, a fixed-price sale of an item from a private individual, a fixed-price sale of an item from an network-based store, and an on-line barter transaction; and wherein the payment information is selected form a group including a credit card number, a checking account number, a shipping address and an e-mail address.
 28. The computer-readable storage medium of claim 25, wherein the sequence of instructions being further configured to cause the machine to: enable the second party to disable the automatic sending of the payment information; and receive the payment information prior to the termination event.
 29. The computer-readable storage medium of claim 25, wherein the sequence of instructions being further configured to cause the machine to: save the payment information for future network-based commerce transactions; and provide the first party an option to always use the payment information for future network-based commerce transactions. 